Systems and methods for electronic signing of electronic content requests

ABSTRACT

Systems and methods are disclosed for cryptographic signing of content requests. One method includes receiving, at a content network, a content request from a publisher website, the publisher website purporting to be associated with a publisher domain. At the content network, a public key may be received associated with the publisher domain. At the content network, at least one policy may be received associated with the publisher domain. It may be determined whether the content request comprises a cryptographic signature. If it is determined that the content request does not comprise a cryptographic signature, content may or may not be provided to the publisher website according to the policy from the publisher domain. If it is determined that the content request comprises a cryptographic signature, the cryptographic signature of the request may be validated using the public key. Upon successfully validating the cryptographic signature of the content request, content maybe provided to the publisher website according to the content request.

TECHNICAL FIELD

Various embodiments of the present disclosure relate generally tocryptographically signing electronic content requests. Morespecifically, exemplary embodiments of the present disclosure relate tosystems and methods of cryptographic signing of electronic contentrequests to validate ownership of websites for fraud prevention.

BACKGROUND

Legitimate websites, online users, and content networks have been thetargets of various forms of fraudulent electronic activity since theadvent of the Internet. Past techniques might install, on the computersof unsuspecting owners, malicious software that engages in abusivebehavior. Such software, for example, may engage in spamming,pagejacking, and/or botnet click fraud.

Techniques for committing botnet click fraud have become increasinglysophisticated. Malicious entities may set up fraudulent websites visitedby no real users yet purporting to be owned by reputable publishers.These fraudulent websites may then request content from contentnetworks, such as advertising networks. The malicious entities may alsooperate a bot network, or botnet, that simulates the browsing oflegitimate web users. These simulated web users may visit the fraudulentwebsites and generate clicks on the provided content. In this manner,content providers and content networks may be defrauded.

SUMMARY OF THE DISCLOSURE

According to certain embodiments, a method is disclosed for validatingthe identity of publisher websites. The method may include receiving, ata content network, a content request from a publisher website, thepublisher website purporting to be associated with a publisher domain;receiving, at the content network, a public key associated with thepublisher domain; receiving, at the content network, at least one policyassociated with the publisher domain; determining, at the contentnetwork, whether the content request comprises a cryptographicsignature; upon determining, at the content network, that the contentrequest does not comprise a cryptographic signature, providing or notproviding content to the publisher website according to the policy fromthe publisher domain; upon determining, at the content network, that thecontent request comprises a cryptographic signature, validating thecryptographic signature of the request using the public key; and uponsuccessfully validating the cryptographic signature of the contentrequest, providing content to the publisher website according to thecontent request.

Various embodiments of such a method may include, in variouscombinations: wherein the publisher key is received from a Domain NameServer associated with the publisher domain; wherein the content networkinduces the publisher domain to add cryptographic signatures to contentrequests; upon determining that the content request does not comprise acryptographic signature, forwarding information associated with thecontent request to the publisher domain; upon determining that thecontent request does not comprise a cryptographic signature, forwardingthe content request to the publisher domain with a request for acorresponding cryptographic signature; upon successfully validating thecryptographic signature of the content request, providing content to thepublisher website for additional content requests from the publisherwebsite without validation; receiving a plurality of content requestsfrom the publisher domain; and validating cryptographic signaturesassociated with the content requests in a batch. Various embodiments ofsuch a method may also include, in various combinations; determiningthat the policy from the publisher domain requires all content requestsassociated with the publisher domain to be cryptographically signed; andupon determining that the content request does not comprise acryptographic signature, denying the content request.

According to certain embodiments, a system is disclosed for validatingthe identity of publisher websites. The system may include a datastorage device storing instructions for validating the identity ofpublisher websites; and a processor configured to execute theinstructions to perform a method including receiving, at a contentnetwork, a content request from a publisher website, the publisherwebsite purporting to be associated with a publisher domain; receiving,at the content network, a public key associated with the publisherdomain; receiving, at the content network, at least one policyassociated with the publisher domain; determining, at the contentnetwork, whether the content request comprises a cryptographicsignature; upon determining, at the content network, that the contentrequest does not comprise a cryptographic signature, providing or notproviding content to the publisher website according to the policy fromthe publisher domain; upon determining, at the content network, that thecontent request comprises a cryptographic signature, validating thecryptographic signature of the request using the public key; and uponsuccessfully validating the cryptographic signature of the contentrequest, providing content to the publisher website according to thecontent request.

Various embodiments of such a system may include, in variouscombinations: wherein the publisher key is received from a Domain NameServer associated with the publisher domain; wherein the content networkinduces the publisher domain to add cryptographic signatures to contentrequests; upon determining that the content request does not comprise acryptographic signature, forwarding information associated with thecontent request to the publisher domain; upon determining that thecontent request does not comprise a cryptographic signature, forwardingthe content request to the publisher domain with a request for acorresponding cryptographic signature; upon successfully validating thecryptographic signature of the content request, providing content to thepublisher website for additional content requests from the publisherwebsite without validation; receiving a plurality of content requestsfrom the publisher domain; and validating cryptographic signaturesassociated with the content requests in a batch. Various embodiments ofsuch a system may also include, in various combinations; determiningthat the policy from the publisher domain requires all content requestsassociated with the publisher domain to be cryptographically signed; andupon determining that the content request does not comprise acryptographic signature, denying the content request.

According to certain embodiments, a non-transitory computer-readablemedium is disclosed for validating the identity of publisher websites.The non-transitory computer-readable medium may store instructions that,when executed by a computer, cause the computer to perform a method forvalidating the identity of publisher websites, the method includingreceiving, at a content network, a content request from a publisherwebsite, the publisher website purporting to be associated with apublisher domain; receiving, at the content network, a public keyassociated with the publisher domain; receiving, at the content network,at least one policy associated with the publisher domain; determining,at the content network, whether the content request comprises acryptographic signature; upon determining, at the content network, thatthe content request does not comprise a cryptographic signature,providing or not providing content to the publisher website according tothe policy from the publisher domain; upon determining, at the contentnetwork, that the content request comprises a cryptographic signature,validating the cryptographic signature of the request using the publickey; and upon successfully validating the cryptographic signature of thecontent request, providing content to the publisher website according tothe content request.

Various embodiments of such a non-transitory computer-readable mediummay include, in various combinations: wherein the publisher key isreceived from a Domain Name Server associated with the publisher domain;wherein the content network induces the publisher domain to addcryptographic signatures to content requests; upon determining that thecontent request does not comprise a cryptographic signature, forwardinginformation associated with the content request to the publisher domain;upon determining that the content request does not comprise acryptographic signature, forwarding the content request to the publisherdomain with a request for a corresponding cryptographic signature; uponsuccessfully validating the cryptographic signature of the contentrequest, providing content to the publisher website for additionalcontent requests from the publisher website without validation;receiving a plurality of content requests from the publisher domain; andvalidating cryptographic signatures associated with the content requestsin a batch. Various embodiments of such a non-transitorycomputer-readable medium may also include, in various combinations;determining that the policy from the publisher domain requires allcontent requests associated with the publisher domain to becryptographically signed; and upon determining that the content requestdoes not comprise a cryptographic signature, denying the contentrequest.

Additional objects and advantages of the disclosed embodiments will beset forth in part in the description that follows, and in part will beapparent from the description, or may be learned by practice of thedisclosed embodiments. The objects and advantages of the disclosedembodiments will be realized and attained by means of the elements andcombinations particularly pointed out in the appended claims.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various exemplary embodiments andtogether with the description, serve to explain the principles of thedisclosed embodiments.

FIG. 1 is a schematic diagram of an environment in which electroniccontent providing may be performed and a system for electronic contentdistribution, according to an exemplary embodiment of the presentdisclosure;

FIG. 2 is a flow diagram of a method for cryptographic signing ofcontent requests, according to an exemplary embodiment of the presentdisclosure;

FIG. 3 is a flow diagram of a method cryptographic signing of contentrequests, according to an exemplary embodiment of the presentdisclosure; and

FIG. 4 provides a functional block diagram illustration of generalpurpose computer hardware platforms.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to the exemplary embodiments of thedisclosure, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

FIG. 1 is a schematic diagram of an environment in which the provision,transmission, and/or distribution of electronic content (e.g.,electronic display ads) may be performed consistent with these methodsand systems for cryptographic signing of content requests, according toan exemplary embodiment of the present disclosure. Specifically, FIG. 1illustrates an exemplary environment including a plurality of userdevice(s) 102, content provider web server(s) 104, publisher webserver(s) 106, the publisher web server(s) 106 each being, or purportingto be, associated with at least one domain 107, DNS server(s) 108,content server(s) 110, and content pixel server(s) 112, all disposed incommunication with an electronic network 100, such as the Internet. Itshould be appreciated that the word “content” as used herein should beconstrued so as to include advertising content (e.g., “ads”), whether inthe form of electronic display ads, electronic videos, electronic GIFs,electronic text messages, or any other audio/visual representation ofelectronic content having a, human/user-facing communicative purpose.

In one embodiment, user devices 102 may be owned and used by one or morepeople, who may be viewers of webpages over the Internet, either througha mobile browser or web browser stored on respective user devices. Userdevices 102 may include any type of electronic device configured to sendand receive data, such as websites and electronic advertisements, overelectronic network 100. For example, user devices 102 may include aserver, personal computer, tablet computer, mobile device, smartphone,personal digital assistant (“PDA”), and/or any Internet-enabled devicedisposed in communication with electronic network 100. For example, inone embodiment, each of user devices 102 may be a handheld device, suchas an Apple iPhone, Apple iPad, Samsung Galaxy, Amazon Kindle, MicrosoftSurface, or any other equivalent or similar device. Each user device 102may have a web browser or mobile browser installed for receiving anddisplaying web and/or ad content from web servers. Thus, each userdevice 102 may be configured to receive and display data that isreceived from one or more of content provider web servers 104, publisherweb servers 106, DNS servers 108, content servers 110, and/or contentpixel servers 112, over electronic network 100.

As an example, in a common situation, a user may be visiting a publisherwebsite (for example www.news.com) using a user device 102. Thepublisher website may include web content and a content pixel tag from acontent pixel server 112. It should be appreciated that the contentpixel tag may alternatively be thought of or referred to as a contentpixel server configured to serve content tags or content requests suchas “ad calls.” In general, when a user device 102 visits a publisherwebsite, the user device 102 may receive from the publisher both the webcontent and an electronic content request (sometimes referred to as an“ad call.” Specifically, the user device 102 may receive, e.g., from awww.news.com web server 106 via a DNS server 108, both the contentassociated with the publisher website and, based on a content pixel tag,a content request including instructions, or code, for receiving anetwork cookie. The content request may call a content server 110 incontent network 114.

Content provider web servers 104 may be owned and/or operated by anyentities having content, and may provide online advertisements or otherforms of media (e.g., embedded video, audio, visual displays, displayads, banner ads, pop-ups, etc.) desired to be delivered to online users.Content providers may interact with user devices 102, publisher webservers 106, DNS servers 108, content servers 110, and/or content pixelservers 112, through content provider web servers 104 connected toelectronic network 100. Thus, content providers may be able tocommunicate information, such as ad information, targeting information,consumer information, budget information, bidding information, etc., toother entities in the environment of FIG. 1.

Publisher web servers 106 may be owned and/or operated by any entitieshaving inventories of available online content space. For example,publishers may include online content providers, search engines, e-mailprograms, or any other online site or program having online usertraffic. Publishers may interact with user devices 102, content providerweb servers 104, DNS servers 108, content servers 110, and/or contentpixel servers 112, through publisher web servers 106 connected toelectronic network 100. Thus, publishers may be able to communicateinventory information, such as site information, demographicinformation, cost information, etc., to other entities in theenvironment of FIG. 1.

DNS servers 108 may include name servers that host a network service forproviding responses to queries against a directory service.Specifically, DNS servers 108 may map a human-recognizable identifier toa systematic, e.g., numeric, identification or addressing componentaccording to a network service protocol, such as numeric InternetProtocol (IP) addresses. DNS servers 108 may also identify and locatecomputer systems, servers, and other resources on the Internet. DNSservers 108 may also store cryptographic keys, such as public keys,policy information related to, for example, content approval policies,approved/banned IP address listings, and/or other forms of data onbehalf of publisher web server(s) 106, content provider web server(s)104, and/or content networks 114. DNS servers 108 may interact with userdevices 102, content provider web servers 104, publisher web servers106, content servers 110, and/or content pixel servers 112 overelectronic network 100.

Content servers 110 and content pixel servers 112 may include any typeof servers configured to process content information from contentproviders and/or site information from publishers, and send and receivecontent requests and information from user devices 102, either directlyor indirectly. In one embodiment, content servers 110 and/or contentpixel servers 112 may be owned and operated by a content network 114.Content network 114 may be a business that receives content buys fromcontent providers, and serves electronic content on inventory suppliedby publishers. Thus, content network 114 may collect money from contentproviders, and purchase impressions from publishers.

In certain embodiments, content servers 110 and content pixel servers112 may be remote web servers that receive advertising information fromadvertisers and serve electronic content items to be placed bypublishers. Content servers 110 and content pixel servers 112 may beconfigured to serve electronic content items across various domains ofpublishers, for example, based on information provided by contentproviders. Content servers 110 and content pixel servers 112 may also beconfigured to serve electronic content items based on contextualtargeting of web sites, search results, and/or user profile information.In some embodiments, content servers 110 and content pixel servers 112may be configured to serve ads based on ad tags served by contentprovider web servers 104 and/or publisher web servers 106, and on adrequests received from user devices 102. Content servers 110 and contentpixel servers 112 may be configured to send and receive data from userdevices 102, content provider web servers 104, publisher web servers106, and/or DNS servers 108, over electronic network 100.

Content networks 114, such as advertising networks, provide content toonline publishers, such as those operating publisher web server(s) 106,and may provide compensation to publishers for the service. Contentproviders may wish to place their content on certain publishers, and mayprovide instructions to the content networks 114 as to where to placecontent. For example, a content provider may wish to place promotionalcontent on a website domain of certain criteria, and may enlist acontent network 114 to accomplish this goal. In one situation, thecontent network 114 may receive a content request from a publisher webserver 106 to serve content to a publisher uniform resource locator(URL), the publisher URL purporting to be associated with a domainmatching the certain criteria. The content network 114 may retrievecontent, for example, from a data store and provide it via a contentserver 110 to the publisher web server 106 for publishing. The publisherweb server 106 may charge fees to the content network 114 for thisservice.

A problem arises because content networks 114 typically rely on somedegree of human analysis and trust to verify, or not verify, that thepublisher URL is indeed owned by, or otherwise legitimately associatedwith the desired domain. Malicious entities have become increasinglysophisticated at appearing to be associated with a certain domain(“spoofing” a domain), though they might actually be hosting afraudulent webpage that is not visited by humans, but instead is onlyfrequented by bots that visit and/or click on the content to generaterevenue.

For example, a content provider may wish to purchase promotional contentspace on www.news.com. A content network 114 may receive a request froma publisher web server 106 seeking promotional content for a website URLthat is apparently owned by www.news.com. The content network 114 mayprovide the electronic content to the website URL, and pay the publisherof the website URL, for example, per thousand impressions (CPM), perclick, etc. However, it may turn out that the website URL is not in factowned by or affiliated with www.news.com. Further, any clicks or viewsgenerated by the website URL may in fact be generated by bots. Botnetworks, or botnets, employ software to mimic users navigating a webbrowser in order to generate fake views or clicks and collect fees fromcontent networks 114 and content providers 104.

Techniques discussed herein allow publishers to cryptographically provethat they are the legitimate owners of a domain, and may allow contentnetworks 114 to deny any requests that are fraudulently claiming to beassociated with legitimate domains.

FIG. 2 is a flow diagram of a method for cryptographic signing ofcontent requests, according to an exemplary embodiment of the presentdisclosure. Publisher domains 107 may publish public keys forcryptographic signature validation purposes, and one or more policiesregarding URL validation requirements for the domain. At step 205, apublisher web server 106 may request, from a content server 110, contentfor display on a publisher URL. While a publisher web server 106 isdepicted in FIG. 2, the content request may actually be received fromthe user device 102 that has requested content from the publisher webserver 106. The publisher web server 106 may appear to be, and/or claimto be, associated with a certain publisher domain 107. At step 210, thecontent server 110 may request the public key from the publisher domain107 associated with the publisher URL. At step 215, the publisher domain107 may provider the public key. At step 220, the content server 110 mayalso request one or more policies regarding URL validation requirementsfor the publisher domain 107, which may be provided at step 225. Thepublisher domain 107 may be a trusted server owned by the publisherdomain, or may be an associated server or entity, such as one or moreDNS servers 108. Public keys and/or policies may be made available, forexample, via an application programming interface (API).

At step 230, it may be determined if a cryptographic signature ispresent in content request. Such a cryptographic signature may beprovided as, for example, a JavaScript Object Notation web token (JWT).It may also be determined if the one or more policies of the domainrequires that cryptographic signatures be provided with contentrequests. If a cryptographic signature is not required, and the contentrequest does not contain a cryptographic signature, the content server110 may follow a domain policy in accepting or rejecting the contentrequest.

Domain policies may include preferences for reporting activity to thedomain, advertising pools, preferences for what to do in case ofvalidation failure, when to provide static images, etc. For example, apublisher may want to be informed of improper content requests, with allimproper requests served an advertisement for the publisher'ssubscription news offering. Such a policy may potentially provide valueif the request is legitimate traffic, while not carrying any risk to thepublisher of negative publicity.

Alternatively, the content server 110 may reject all content requestslacking a cryptographic signature according to the policy of the contentnetwork 114. Alternatively, the content server 110 may forward thecontent request to the publisher domain 107 along with a request for acryptographic signature. Thus, the content server 110 or other thirdparty may choose to follow domain policies, but may ignore the domainpolicies, at least in certain circumstances.

If a cryptographic signature is required, yet not provided in thecontent request 205, the content server 110 may automatically reject thecontent request. If the cryptographic signature is required, andprovided in the content request, the content server 110 may validate thecryptographic signature using the public key in step 240. If the contentrequest is not successfully validated, the content request may begranted or denied according to the policy of the publisher domain 107.For example, the policy may require informing the publisher domain 107if a cryptographic signature validation associated with the publisherdomain 107 should fail. Alternatively, the content server 110 may denyall content requests when the cryptographic signature validation failsaccording to its own policy.

Validation of the cryptographic signature using the public key may bothensure that the content request is unmodified from its original version,and that it was truly sent by the publisher domain 107. Thecryptographic signature also proves that the publisher was actuallyinvolved in the request, and that any targeting variables in the requestwere set by the publisher. In many reporting and tracking systems,browsers are simply assumed to be telling the truth. However, infraudulent systems, a single content request may present differentinformation to the publisher domain 107, the tracking/reporting systemused by the publisher domain 107 (for example, Omniture), and/or thecontent server 110. As a result, the traffic cannot be linked and thefraud is more difficult to identify. One benefit of techniques presentedherein is that publishers may have more reliable and trackable reportingof their traffic.

If the validation of the cryptographic signature is successful, at step250 content may be provided to the publisher web server 106. Thepublisher web server 106 may then provide the content to one or moreuser devices 102. Alternatively, the content server 110 may provide thecontent directly to the one or more user devices 102.

Validating cryptographic signatures may introduce a delay in webpageload time. Accordingly, if a content request arrives requesting contentfor a URL not previously known to the content network 114, the URL maybe provisionally approved to receive content, and the content network114 may validate the cryptographic signature asynchronously, or inbatch. Further, once a given URL is successfully cryptographicallyvalidated, subsequent requests for content for this URL may beautomatically approved. In this manner, any time delay associated withcryptographic validation of a URL would be limited to the first time theURL is accessed by a user.

Further techniques may be employed to reduce time delay in processing ofcontent requests. For example, public keys and policies for givenpublisher domains may be cached locally in the content network 114, suchas at content servers 110, to save transaction time. A risk-basedanalysis may also be performed by, for example, the content network 114,such as by content server(s) 110. Rather than immediately validating thecontent request, the claimed publisher associated with the request, theIP address of the request, the geographic location associated with theIP address, prior activities of the IP address, whether the IP addressis flagged, etc. may be analyzed to determine if the content requestwill be granted. Such a risk-based analysis may be performed whether ornot the content request is cryptographically signed.

Using any of these techniques, validation of the cryptographic signatureof the content request may be delayed, but may be performed before anypayment is provided to the publisher. In this manner, a content network114 may deny payment to the sender of a content request, even if contenthas been provided to the sender, if it is later determined that thecontent request may be fraudulent. For example, a publisher claiming tobe associated with www.news.com may be provided content in response to acontent request, but may later be denied payment if later validation ofthe cryptographic signature, risk analysis, etc., identifies thepublisher as potentially fraudulent, or as potentially not trulyassociated with wwww.news.com.

The content network 114 may require, as a matter of policy, thatpublisher domains 107 utilize public keys and cryptographic signaturesin order to have their content requests processed successfully. Thecontent network 114 may induce publisher domains 107 contractually, viacontent request denial, and/or via reminders to institute cryptographicsigning in content requests.

In an effort to identify and track fraudulent activity, the contentnetwork 114 may further make data related to all content requestsassociated with a given domain available to the domain. In this way,domains may be able to determine if malicious entities are attempting tospoof the domain.

FIG. 3 is a flow diagram of a method cryptographic signing of contentrequests, according to an exemplary embodiment of the presentdisclosure. At step 305, a content request may be received, at a contentnetwork and from a publisher website, the publisher website purportingto be associated with a publisher domain. At step 310, a public key maybe received, at the content network, associated with the publisherdomain. At step 315, at least one policy may be received, at the contentnetwork, associated with the publisher domain. At step 320, it may bedetermined, at the content network, whether the content requestcomprises a cryptographic signature. At step 325, upon determining, atthe content network, that the content request does not comprise acryptographic signature, content may be or may not be provided to thepublisher website according to the policy from the publisher domain. Atstep 330, upon determining, at the content network, that the contentrequest comprises a cryptographic signature, the cryptographic signatureof the request may be validated using the public key. At step 335, uponsuccessfully validating the cryptographic signature of the contentrequest, content may be provided to the publisher website according tothe content request.

FIG. 4 provides a functional block diagram illustration of generalpurpose computer hardware platforms. FIG. 4 illustrates a network orhost computer platform 400, as may typically be used to implement aserver, such as a content server 110, or any other server used intechniques discussed in techniques presented herein. It is believed thatthose skilled in the art are familiar with the structure, programmingand general operation of such computer equipment and as a result thedrawings should be self-explanatory.

A platform for a server or the like 400, for example, may include a datacommunication interface for packet data communication 460. The platformmay also include a central processing unit (CPU) 420, in the form of oneor more processors, for executing program instructions. The platformtypically includes an internal communication bus 410, program storageand data storage for various data files to be processed and/orcommunicated by the platform such as ROM 430 and RAM 440, although theserver 400 often receives programming and data via networkcommunications 470. The hardware elements, operating systems andprogramming languages of such equipment are conventional in nature, andit is presumed that those skilled in the art are adequately familiartherewith. The server 400 also may include input and output ports 450 toconnect with input and output devices such as keyboards, mice,touchscreens, monitors, displays, etc. Of course, the various serverfunctions may be implemented in a distributed fashion on a number ofsimilar platforms, to distribute the processing load. Alternatively, theservers may be implemented by appropriate programming of one computerhardware platform.

Program aspects of the technology may be thought of as “products” or“articles of manufacture” typically in the form of executable codeand/or associated data that is carried on or embodied in a type ofmachine readable medium. “Storage” type media include any or all of thetangible memory of the computers, processors or the like, or associatedmodules thereof, such as various semiconductor memories, tape drives,disk drives and the like, which may provide non-transitory storage atany time for the software programming. All or portions of the softwaremay at times be communicated through the Internet or various othertelecommunication networks. Such communications, for example, may enableloading of the software from one computer or processor into another, forexample, from a management server or host computer of the mobilecommunication network into the computer platform of a server and/or froma server to the mobile device. Thus, another type of media that may bearthe software elements includes optical, electrical and electromagneticwaves, such as used across physical interfaces between local devices,through wired and optical landline networks and over various air-links.The physical elements that carry such waves, such as wired or wirelesslinks, optical links or the like, also may be considered as mediabearing the software. As used herein, unless restricted tonon-transitory, tangible “storage” media, terms such as computer ormachine “readable medium” refer to any medium that participates inproviding instructions to a processor for execution.

Techniques presented herein improve the technical field in contentprovision networks, and solves problems arising in the post-Internetera. Currently, it is not possible to easily and quickly guarantee thata URL is owned by or associated with a given domain. Techniquespresented herein may provide such a guarantee, and may prevent manymillions of dollars in fraud from occurring each year. In addition,techniques such as asynchronous validation and batching further helpguarantee that content may be provided without sacrificing speed,despite the computationally intense cryptographic validation techniquesthat may be employed. Further, techniques presented herein may providedomains with an enhanced ability to assert policies regarding contentdistribution security within their domain. Further, fraudulent contentrequests commonly present different data to content servers, publisherdomains, and/or publisher domain analytics trackers, thus makingidentifying fraudulent traffic more difficult. Techniques presentedherein help guarantee that data is presented in a unified manner, thusensuring more reliable reporting of content request traffic.

The many features and advantages of the disclosure are apparent from thedetailed specification, and thus, it is intended by the appended claimsto cover all such features and advantages of the disclosure which fallwithin the true spirit and scope of the disclosure. Further, sincenumerous modifications and variations will readily occur to thoseskilled in the art, it is not desired to limit the disclosure to theexact construction and operation illustrated and described, andaccordingly, all suitable modifications and equivalents may be resortedto, falling within the scope of the disclosure.

Other embodiments of the disclosure will be apparent to those skilled inthe art from consideration of the specification and practice of theinvention disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the invention being indicated by the following claims.

1-20. (canceled)
 21. A method for validating the identity of publisherwebsites, the method including: receiving a content request from apublisher website, the publisher website purporting to be associatedwith a publisher domain; receiving at least one policy associated withthe publisher domain; determining whether the content request comprisesa cryptographic signature; upon determining that the content requestdoes not comprise a cryptographic signature, providing or not providingcontent to the publisher website according to the policy from thepublisher domain; upon determining that the content request comprises acryptographic signature, validating the cryptographic signature of therequest; and upon successfully validating the cryptographic signature ofthe content request, providing content to the publisher websiteaccording to the content request.
 22. The method of claim 21, furthercomprising: prompting the publisher domain to add cryptographicsignatures to content requests.
 23. The method of claim 21, furthercomprising: upon determining that the content request does not comprisea cryptographic signature, forwarding information associated with thecontent request to the publisher domain.
 24. The method of claim 21,further comprising: upon determining that the content request does notcomprise a cryptographic signature, forwarding the content request tothe publisher domain with a request for a corresponding cryptographicsignature.
 25. The method of claim 21, further comprising: uponsuccessfully validating the cryptographic signature of the contentrequest, providing content to the publisher website for additionalcontent requests from the publisher website without validation.
 26. Themethod of claim 21, further comprising: receiving a plurality of contentrequests from the publisher domain; and validating cryptographicsignatures associated with the content requests in a batch.
 27. Themethod of claim 21, further comprising: determining that the policy fromthe publisher domain requires all content requests associated with thepublisher domain to be cryptographically signed; and upon determiningthat the content request does not comprise a cryptographic signature,denying the content request.
 28. The method of claim 21, wherein thepublisher key is received from a Domain Name Server associated with thepublisher domain.
 29. A system for validating the identity of publisherwebsites, the system including: at least one data storage device storinginstructions for validating the identity of publisher websites; and atleast one processor configured to execute the instructions to performoperations comprising: receiving a content request from a publisherwebsite, the publisher website purporting to be associated with apublisher domain; receiving at least one policy associated with thepublisher domain; determining whether the content request comprises acryptographic signature; upon determining that the content request doesnot comprise a cryptographic signature, providing or not providingcontent to the publisher website according to the policy from thepublisher domain; upon determining that the content request comprises acryptographic signature, validating the cryptographic signature of therequest; and upon successfully validating the cryptographic signature ofthe content request, providing content to the publisher websiteaccording to the content request.
 30. The system of claim 29, furthercomprising: prompting the publisher domain to add cryptographicsignatures to content requests.
 31. The system of claim 29, the methodfurther comprising: upon determining that the content request does notcomprise a cryptographic signature, forwarding information associatedwith the content request to the publisher domain.
 32. The system ofclaim 29, the method further comprising: upon determining that thecontent request does not comprise a cryptographic signature, forwardingthe content request to the publisher domain with a request for acorresponding cryptographic signature.
 33. The system of claim 29, themethod further comprising: upon successfully validating thecryptographic signature of the content request, providing content to thepublisher website for additional content requests from the publisherwebsite without validation.
 34. The system of claim 29, the methodfurther comprising: receiving a plurality of content requests from thepublisher domain; and validating cryptographic signatures associatedwith the content requests in a batch.
 35. The system of claim 29, themethod further comprising: determining that the policy from thepublisher domain requires all content requests associated with thepublisher domain to be cryptographically signed; and upon determiningthat the content request does not comprise a cryptographic signature,denying the content request.
 36. The system of claim 29, wherein thepublisher key is received from a Domain Name Server associated with thepublisher domain.
 37. A non-transitory computer-readable medium storinginstructions that, when executed by a computer, cause the computer toperform operations validating the identity of publisher websites, theoperations comprising: receiving a content request from a publisherwebsite, the publisher website purporting to be associated with apublisher domain; receiving at least one policy associated with thepublisher domain; determining whether the content request comprises acryptographic signature; upon determining that the content request doesnot comprise a cryptographic signature, providing or not providingcontent to the publisher website according to the policy from thepublisher domain; upon determining that the content request comprises acryptographic signature, validating the cryptographic signature of therequest; and upon successfully validating the cryptographic signature ofthe content request, providing content to the publisher websiteaccording to the content request.
 38. The computer-readable medium ofclaim 37, the operations further comprising: upon determining that thecontent request does not comprise a cryptographic signature, forwardingthe content request to the publisher domain with a request for acorresponding cryptographic signature.
 39. The computer-readable mediumof claim 37, the operations further comprising: upon successfullyvalidating the cryptographic signature of the content request, providingcontent to the publisher website for additional content requests fromthe publisher website without validation.
 40. The computer-readablemedium of claim 37, the operations further comprising: receiving aplurality of content requests from the publisher domain; and validatingcryptographic signatures associated with the content requests in abatch.